Temporary messaging address system and method

ABSTRACT

A messaging system is disclosed. The system includes a communications network including a wireless access point, a messaging server coupled to the communications network, and a mobile device in communication with the communications network via an access point. The mobile device has a mobile ID associated with the device, and a program running on the mobile device from which a temporary address may be created corresponding to the mobile ID. The temporary address is useable for messaging over the communications network. The temporary address is registered with the messaging server.

BACKGROUND

[0001] The traditional messaging systems (email and instant messaging)are designed around the philosophy of a fixed messaging server andstatic messaging addresses through which messages may be sent to reachthe intended user. Once a messaging address is known, it may be usedrepeatedly to send messages. The address may also be used independent oftime and location of either the sender or recipient.

[0002] In a more mobile environment, where users are using mobilewireless devices (such as a handheld or portable computer), traditionalmessaging systems may not be optimal. While the idea of a staticmessaging address is appealing, it is often not the most practical. Oncea messaging address has been given out, there is no explicit mechanismto change or revoke an address. To revoke an address, the user musteither cancel the messaging account (or no longer access it), or filterout messages from unwanted users. The former mechanism requires the userto notify people of a change in address (for those that should still beable to send messages), and the latter requires complex software andconstant configuration on the client side. In addition, the secondmethod places an increased load on the mobile device and itscommunication links.

[0003] An additional problem for messaging in a mobile networkenvironment is the use of localized resources and ad hoc networks.

[0004] Accordingly, there is a need for a messaging system in a mobilenetwork which utilizes temporary messaging addresses associated withunique mobile identifications.

[0005] There is also a need for a messaging server that is enabled toassociate temporary messaging addresses with mobile devices. Further,there is a need for a method of communicating between a first mobilecommunications device and a second mobile communications device usingtemporary messaging addresses and, further, depending on specifiedconditions. Further still, there is a need for a method of alertingpatrons of available services by utilizing temporary messaging addressesassociated with individual mobile devices.

[0006] It would be desirable to provide a system and/or method thatprovides one or more of these or other advantageous features. Otherfeatures and advantages will be made apparent from the presentspecification. The teachings disclosed extend to those embodiments whichfall within the scope of the appended claims, regardless of whether theyaccomplish one or more of the aforementioned needs.

SUMMARY

[0007] An exemplary embodiment of the invention relates to a messagingsystem. The messaging system includes a communications network includinga wireless access point, a messaging server coupled to thecommunications network, and a mobile device in communication with thecommunications network via an access point. The mobile device has amobile ID associated with the device and a program running on the mobiledevice from which a temporary address may be created corresponding tothe mobile ID. The temporary address is useable for messaging over thecommunications network the temporary address being registered with themessaging server.

[0008] Another exemplary embodiment of the invention relates to a methodof providing messaging services to a user of a mobile communicationsdevice. The method includesproviding a mobile device having a mobile IDassociated therewith and running a messaging program on the device. Themethod also includes creating, via the program, a temporary messagingaddress, communicating the temporary messaging address to a messagingserver, and sending a message using the temporary messaging address.

[0009] Further, an exemplary embodiment of the invention relates to amessaging server. The messaging server includes a protocol adapter forreceiving messages from mobile communications devices, each mobilecommunications device having a unique mobile ID associated therewith, amessaging queue for ordering the delivery of incoming and outgoingmessages, sent from the mobile communications devices, and an addresstranslator enabled to determine the mobile ID associated with thetemporary delivery address identified in the incoming message.

[0010] Further still, an exemplary embodiment of the invention relatesto a method of alerting a patron of an available service. The methodincludes creating a temporary messaging address associated with a mobiledevice having a unique mobile ID and sending a message to the temporaryaddress through a server. The message includes a notification of theservice availability. The method also includes translating the temporarymessaging address to the mobile ID, by the server, and sending themessage to the mobile device associated with the mobile ID.

[0011] Yet still another exemplary embodiment of the invention relatesto a method of communicating between a first mobile communicationsdevice and a second mobile communications device. The methodincludescreating a first temporary messaging address associated with thefirst mobile communications device, creating a second temporarymessaging address associated with the second mobile communicationsdevice, and providing conditions under which messages may be deliveredbetween the two devices. The method also includes sending a message fromthe first mobile communications device to the second mobilecommunications device using the second temporary messaging address,determining if the conditions for sending the message are satisfied, anddelivering the message to the second temporary address if the conditionsare satisfied.

[0012] Alternative exemplary embodiments relate to other features andcombination of features as may be generally recited in the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The invention will become more fully understood from thefollowing detailed description, taken in conjunction with theaccompanying drawings, wherein like reference numerals refer to likeelements, in which:

[0014]FIG. 1 is a block diagram of a messaging server;

[0015]FIG. 2 is a block diagram of a messaging system; and

[0016]FIG. 3 is a block diagram of a communications system.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

[0017] If a mobile user wants to have messaging capabilities with usersin a localized geographical area it may be advantageous to use localizedservers and addresses. This would offer the following advantages:

[0018] Better performance, less performance problems from larger areanetworks (e.g., delay, bandwidth).

[0019] Lack of global networking connections. Often a local area mayoffer a localized network with no general internet connectivity.Messaging could be accomplished via local servers with temporaryaddresses. This may especially be applicable in ad hoc networks.

[0020] The ability to explicitly exploit location and time informationin messaging.

[0021] The ability to use, modify, or revoke messaging addresses.

[0022] The ability to switch from local to global messaging servers (uselocal service when available, but switch to global when leaving localarea).

[0023] A mobile user may also have more than one mobile device (e.g.,cell phone, PDA, pager, etc). Each one of these devices may be used forcommunication to the mobile user. In addition, the mobile user may havea preference as to which is used. It should be possible for a mobileuser to register multiple devices, but specify a preference to which isused. In addition, some mobile devices do not permit directcommunications between servers and devices (e.g., cell phones andpagers). Messages to these device may need to be passed through anexternal service (e.g., telephone system). This document discussesprimarily data devices and local wireless devices, but the system andideas disclosed may be applied to other, larger coverage area wirelesstechnologies.

[0024] The disclosure relates to a system by which messaging addressescan be dynamically assigned to allow more user control over messaging. Asystem is available which can dynamically create new messaging addressesfor a mobile user on demand. The mobile user can give out differentmessaging addresses to different people, and can revoke (cancel) anaddress anytime thereby preventing messages from reaching the user.

[0025] This messaging system also is ideally suited for localizedmessaging, as might be found in a shopping mall or other sites in whichlocalized messaging may be useful.

[0026] A further component of a messaging system of the type disclosedis the use of location and time specification in message submission.When a message is sent, it may include both time and locationconditions. Messages will only be delivered if the mobile user is in thespecified location at the specified time.

[0027] The messaging system disclosed may include any one of or anycombination of the following characteristics:

[0028] 1. The mail recipient has control over the duration of existenceof the messaging address.

[0029] 2. Should support both e-mail (time insensitive), and instantmessaging (time sensitive) standards.

[0030] 3. The system should preventspam (e-mail from unknown people) orunauthorized messages.

[0031] 4. The system should support existing email and messagingstandards.

[0032] 5. Messages should be cancelable by the sender.

[0033] 6. People can request to be notified of cancelled addresses.

[0034] 7. Users can cancel mail addresses at anytime.

[0035] 8. Messaging system can not be used for tracking.

[0036] 9. A mobile user can use multiple messaging addresses.

[0037] Associated with each mobile device may be one or more mobile IDS.A mobile ID may be a universal resource locator (URL) which specifiesthe location of services for a mobile device or any other uniqueidentifier associated with an individual mobile device. URLs provide astandard format for specifying a resource (message service) independentof specific service or protocol. Examples include but are not limitedto:

[0038] mailto:customer1@mall.com

[0039] instantMessage://mobile.mall.com/customer1

[0040] email://customer1.mall.com

[0041] message:customer1@xxx.yyy.com

[0042] The mobile ID may be used for services other than messaging andprovides a common format for such services. As an example, a mobiledevice may be assigned mobile ID:

[0043] MobileID://mobile.mall.com/customer1

[0044] The email or instant messaging address could be obtained from theMobile ID by replacing the protocol specification with the appropriateservices requested. For example:

[0045] Email://mobile.mall.com/customer1

[0046] The system may be configured to support two (or more) types ofaddressable entities, such as mobile devices and mobile users.

[0047] A mobile user may have multiple mobile devices (e.g., a laptopcomputer, a handheld computer, a pager, a mobile telephone, etc.).Messages may be redirected between the different mobile devices (e.g.,e-mail messages redirected to a pager).

[0048] Referring now to FIG. 1, in an exemplary embodiment a messagingserver 100 may be a localized server which provides messaging services.It may be responsible for receiving messages, buffering messaging, andsending messages to the mobile devices among other tasks.

[0049] The architecture of message server 100 includes two processingqueues. The first queue (processing queue 110) holds incoming messages105 and messages waiting for condition (location and time) satisfaction.A message is removed from the queue when all conditions are satisfied,for example, time and/or location conditions.

[0050] An address translator 120 is responsible for translating anaddress of message 105. The mobile ID of message 105 is converted intoan address used for delivery to a mobile device 125. Address translator120 may also be used to redirect messages to different mobile devices(if specified by the mobile user).

[0051] A delivery queue holds messages until the mobile ID can betranslated into a physical address. The delivery queue may include apush delivery queue 130 and a pull delivery queue 135. The push deliveryqueue attempts to deliver a message when mobile device 125 isaccessible. If mobile device 125 is unavailable, the message is held inthis queue until a physical address is available. Pull delivery queue135 is used for queuing messages which must be pulled by the client.Messages are stored until requested by the client. The queue may supportlegacy protocols, such as but not limited to IMAP, POP or others.

[0052] Mobile device events are notifications in the change of location(or other properties) of mobile device 125. These events are used totrigger the condition of messages waiting in the processing queue. Amobile device state information unit 140 keeps track of the currentlocation of mobile device 125 and its current physical address. Thecurrent location may be supplied through a location determinationservice on or linked to the network.

[0053] A mobile ID control unit 145 is responsible for keeping track ofmobile IDs. Messages may also be sent to mobile device control unit 145.These message represent control messages used to allocate, modify, andchange mobile IDs.

[0054] Acknowledgement messages (containing a message ID) are sent oncethe message has left the delivery queue.

[0055] The basic functionality of the server may include but is notlimited to:

[0056] Support existing messaging standards. The server can act as aserver for existing messaging protocols. For exampleIMAP, POP, InstantMessaging (Jabber, AOL, MS, etc).

[0057] Receive location events. When the network detects that a mobiledevice has moved location, a location event is sent to message server100. The condition on pending messages are evaluated to see if theyshould be released. For example, notification of when the mobile devicemoves and/or sending messages on condition evaluation.

[0058] Buffering messages. For example, messaging waiting for eventsand/or messaging waiting for delivery.

[0059] Receive message. For example, return message ID, and/or make orcontain time and location conditions.

[0060] Cancel message. For example, message specified by message ID.

[0061] Send message. For example, return messages associated with mobileID.

[0062] Direct messages. For example, the message server can forwardmessages to another server.

[0063] Revoke message address. For example, turn off a message address.

[0064] Message delivery confirmation. For example, recipient controlled.

[0065] The protocol adapters are used to support the different protocolsand encoding with different existing messaging systems.

[0066] In an exemplary embodiment, the following communications may besupported by message server 100:

[0067] Register mobile_user, used to register a mobile user.

[0068] Register mobile_device, used to register amobile_device.

[0069] Set mobile_user preferences, such as a message describing anyprocessing to be applied to messages, for example, message redirectionand/or message filtering.

[0070] Send message, used to send a message.

[0071] Receive message, used to get a message.

[0072] Unregistermobile_user, used to cancelmobile_user and allassociated mobile_devices.

[0073] Unregistermobile_ID, used to cancel mobile_ID.

[0074] Query messageServer, used to get a description of message servercapabilities and configurable capabilities.

[0075] In an exemplary embodiment, the messaging client such as mobiledevice 125 should support the following operations:

[0076] Send message wherein theMessage_ID may be returned.

[0077] Receive/display message.

[0078] Create new mobile_ID.

[0079] Delete mobile_ID.

[0080] Location specification.

[0081] Time specification.

[0082] Cancel message.

[0083] View all messages including those deleted and/or including thosewaiting for events.

[0084] Further, in an exemplary embodiment a legacy messagingapplication 210 (see FIG. 2) may be augmented with a client assistapplication 220.

[0085] The system should be compatible with existing messaging systems.Likewise, existing messaging clients should be compatible with thissystem, although full functionality may or may not be possible.

[0086] Referring now to FIG. 3, messaging server 100 is coupled to alocal communications network 310 for sending messages to users connectedto local communications network 310 or, alternatively, to an externalcommunications network 320. As described above, local communicationsnetwork 310 includes access points 330 that provide wireless access frommobile devices 340 to local communications network 310. In the exemplaryembodiments disclosed, mobile device 340 is enabled to create temporaryaddresses utilized by devices accessing local communications network 310via messaging server 100.

[0087] The mobile ID can be used to determine the email or instantmessaging address of the mobile user. These addresses can be passed toexisting email and instant messaging systems so that they can sendmessages.

[0088] Any e-mail or instant messaging client can be used to sendmessaging in this system.

[0089] The mobile user can also use standard instant messaging/emailclients. The client application would need to be configured to bindthemselves to the proper servers, and supply correct user ID/passwordsfor message retrieval. Not all existing messaging client supportmultiple addresses.

[0090] A legacy e-mail 210 or instant messaging system may be unable tospecify location specific properties of a message, cancel messages, orbe notified of address cancellation as the existing application andprotocol do not typically support these types of operations.Accordingly, messaging assist application 220 may provide an interfacefor e-mail application 210 and message server 100, wherein messageserver 100 is enabled to handle mobile users using temporary messagingaddresses.

[0091] In yet a further exemplary embodiment, a cell phone voice systemmay be accessible through a plain old telephone system (POTS). Voicecalls may be sent through the telephone system and a mobile user wouldneed to register the telephone number. Voice messages may also be sentthrough the POTS and a mobile user needs to register the telephonenumber. Text messages (e.g., SMS) may also be sent through a carriermessage service and a mobile user needs to register a message address.Further, pager messages may be sent through the POTS of message serviceand a mobile user needs to register a telephone number or messageservice address.

[0092] When a message is sent, location conditions may be placed on themessage. Location may be specified in many ways, including but notlimited to, absolute coordinates (GPS, latitude, longitude), relativecoordinates (to message server, mobile device, or other objects), zones(location specific zones), transitions into or out of zones, and otherformats.

[0093] Location specifications may not be allowed which enable tracking.It may be valid for a mobile user 1 to specify that a message should besent to mobile user 2 when they are within 100 meters, but not valid formobile user 1 to request a message to be sent to himself when they aremore than 100 meters apart. This could only be done with cooperation ofmobile user 2. The location information may be encoded into messagesdepending upon message encoding scheme including, but not limited to,MIME extension for e-mail orXML tag.

[0094] To determine which location formats are accepted by messageserver 100, limits of location values, and defined zones, a message maybe sent to message server 100 requesting the information. Theinformation may be supplied inXML encoded format, for example.

[0095] A message address may be deleted be either the mobile user or themessage service provider. Also, it is desirable to eliminate unusedmobile IDs. A customer, for example, may have the option to specify howlong the address is valid.

[0096] The messaging service provider (e.g., mall management) may alsoexplicitly or implicitly limit the validity of the mobile addresses.Options may include, but are not limited to, adding temporary addressesdeleted at regular times, such as when the mall closes. Having mobileIDs deleted after a period of non-use, for example, one day with nomessages, or two days with stored messages. Also, mobile IDs may bedeleted at a user specified time. Further, a mobile ID may be deletedwhen the customer leaves the mall. In an exemplary embodiment, leavingthe mall may be differentiated from turning the device off.

[0097] Messages or mobile IDs may also be deleted if the number ofmessages being stored or delivered becomes excessive (e.g., in the caseof SPAM or mail bomb reaction).

EXAMPLE 1

[0098] Consider a retail shopping mall. Customers may use mobile devices(such as PDAs) with wireless connections for various location basedservices. A customer requests a service (such as 1 hour photo service)in a store within the mall. The service will be complete at some time inthe future and the customer wishes to be notified when the service(photo developing) is complete.

[0099] The customer can communicate through a wireless technology (suchas 802.11 or Bluetooth) to a mall network support services for mobiledevices. The customer can request a mobile ID from the network. This IDis then passed to the photo store as the address to use for sendingnotices. When the customer' film is developed, the store can send amessage to him using his mobile ID.

[0100] The store may also choose to send a location specific message. Ifthe customer is detected outside of the mall, they may send him anothermessage reminding him of the developed film.

[0101] Once the film is collected, location based messages should becancelled (you don't want to bother the customer).

EXAMPLE 2

[0102] The same customer (as in example 1) is hungry, and wants to eat.He selects a restaurant in the mall he wants to eat at, but it has awaiting list. Through his mobile device he requests a reservation (or tobe put on waiting list). He gives his mobile ID (same as example 1) tothe restaurant and asks to be notified when his table is ready.

[0103] When the customer's name is getting near the top of the list, therestaurant wants to warn the customer that his table will be ready soon.The restaurant sends the following messages:

[0104] When the customer is fifth on the list, send message to the farlocations of the mall.

[0105] When the customer is third on the list, they send message to themedium distances away part of the mail and the previous message iscancelled.

[0106] When the customer is first on the list, they send message to alllocations in mall and the previous message is cancelled.

[0107] When the customer receives the message, he can reply toacknowledge he still wants the table.

EXAMPLE 3

[0108] The same customer goes into a store and asks a clerk for help infinding an item. The clerk says she will need to go and check thebackroom. She will message him when she knows if the item is available.

[0109] The customer requests a new mobile ID, and gives it to the clerk.After looking around the store, he decides he is not interested in theitem, and cancels the mobile ID. There is no reason for the store tobother the customer. He can still receive other messages (examples 1 and2). The clerk may be notified of the cancelled ID, if she requestednotification in advance.

EXAMPLE 4

[0110] A husband and wife are shopping separately in the mall. If theyare near each other they would like to be informed. Both husband andwife send each other a message with a separation condition of 100meters. When they are within 100 meters, their messages are delivered.They may then communicate to see where the other is.

EXAMPLE 5

[0111] A meeting is schedule for 5:00 p.m. in conference room A. Whenthe meeting is scheduled, a message is sent to everyone in the meetingwith the following conditions

[0112] Time 5:00 p.m.

[0113] Location (conference room A).

[0114] A reminder message is sent. If the meeting is altered, themessages may be cancelled.

EXAMPLE 6

[0115] A mobile user enters a mall. He registers himself as a mobileuser. He registers his handheld computer and pager. He queries themessage server and determines the server can support messageredirection. He sends a configuration message to the message serverstating than any messages destined for his handheld computer should beredirected to his pager. Whenever a message is sent to his handheldcomputer, the message server redirects it to his pager. When he leavesthe mall, he unregisters hismobile_user, and all addresses are deleted.

[0116] While the detailed drawings, specific examples and particularformulations given describe preferred and exemplary embodiments, theyserve the purpose of illustration only. The inventions disclosed are notlimited to the specific forms shown. For example, the methods may beperformed in any of a variety of sequence of steps. The hardware andsoftware configurations shown and described may differ depending on thechosen performance characteristics and physical characteristics of thecomputing devices. For example, the type of computing device,communications bus, or processor used may differ. The systems andmethods depicted and described are not limited to the precise detailsand conditions disclosed. Furthermore, other substitutions,modifications, changes, and omissions may be made in the design,operating conditions, and arrangement of the exemplary embodimentswithout departing from the scope of the invention as expressed in theappended claims.

What is claimed is:
 1. A messaging system comprising: a communicationsnetwork including a wireless access point; a messaging server coupled tothe communications network; a mobile device in communication with thecommunications network via an access point, the mobile device having amobile ID associated with the device; and a program running on themobile device from which a temporary address may be createdcorresponding to the mobile ID, the temporary address being useable formessaging over the communications network the temporary address beingregistered with the messaging server.
 2. The system of claim 1, whereinthe program enables the deletion of a temporary address that iscorresponding to the mobile ID.
 3. The system of claim 1, wherein theprogram enables the deletion of a temporary address that iscorresponding to the mobile ID.
 4. The system of claim 1, wherein theprogram enables the deletion of a temporary address that iscorresponding to the mobile ID.
 5. The system of claim 1, wherein theprogram enables communication of the temporary address to th e messagingserver.
 6. The system of claim 1, wherein the program enables theforwarding of incoming messages via the temporary address to alternativecommunications devices.
 7. The system of claim 1, wherein the server isassociated with a shopping mall environment.
 8. The system of claim 1,wherein the server is associated with a campus environment.
 9. Thesystem of claim 1, wherein the mobile device is a handheld computer. 10.The system of claim 1, wherein the communications network is a localarea network (LAN).
 11. A method of providing messaging services to auser of a mobile communications device, comprising: providing a mobiledevice having a mobile ID associated therewith; running a messagingprogram on the device; creating, via the program, a temporary messagingaddress; communicating the temporary messaging address to a messagingserver; and sending a message via the messaging server using thetemporary messaging address.
 12. The method of claim 11, furthercomprising: receiving, by the mobile communications device via themessaging server, a message addressed to the temporary messagingaddress.
 13. The method of claim 11, further comprising: creatingmultiple temporary messaging addresses associated with the mobile ID.14. The method of claim 13, further comprising: deleting multipletemporary messaging addresses associated with the mobile ID.
 15. Themethod of claim 11,further comprising: deleting a temporary messagingaddress associated with the mobile ID.
 16. The method of claim 11,further comprising: associating the temporary messaging address withmultiple mobile communication devices each mobile communication devicehaving a unique mobile ID.
 17. A messaging server comprising: a protocoladapter for receiving messages from mobile communications devices, eachmobile communications device having a unique mobile ID associatedtherewith; a messaging queue for ordering the delivery of incoming andoutgoing messages, sent from the mobile communications devices; and anaddress translator enabled to determine the mobile ID associated withthe temporary delivery address identified in the incoming message. 18.The server of claim 17, wherein the messaging queue includes a pushdelivery messaging queue and a pull delivery messaging queue.
 19. Theserver of claim 17, wherein the server is enabled to delete thetemporary messaging address under specified conditions.
 20. A method ofalerting a patron of an available service, comprising: creating atemporary messaging address associated with a mobile device having aunique mobile ID; sending a message to the temporary address through aserver, the message including a notification of the serviceavailability; translating the temporary messaging address to the mobileID, by the server; and sending the message to the mobile deviceassociated with the mobile ID.
 21. A method of communicating between afirst mobile communications device and a second mobile communicationsdevice, comprising: creating a first temporary messaging addressassociated with the first mobile communications device; creating asecond temporary messaging address associated with the second mobilecommunications device; providing conditions under which messages may bedelivered between the two devices; sending a message from the firstmobile communications device to the second mobile communications deviceusing the second temporary messaging address; determining if theconditions for sending the message are satisfied; and delivering themessage to the second temporary address if the conditions are satisfied.22. The method of claim 21, further comprising: disabling the temporarymessaging address.